home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / std / c++ / 1048 < prev    next >
Encoding:
Text File  |  1996-08-06  |  1.6 KB  |  42 lines
  1. Path: engnews1.Eng.Sun.COM!taumet!clamage
  2. From: Rich Paul <linguist@cyberspy.com>
  3. Newsgroups: comp.std.c++
  4. Subject: char_traits<T> return values
  5. Date: 12 Apr 1996 14:57:19 GMT
  6. Organization: Technical Resource Connection
  7. Approved: clamage@eng.sun.com (comp.std.c++)
  8. Message-ID: <316DB8A8.2556@cyberspy.com>
  9. NNTP-Posting-Host: taumet.eng.sun.com
  10. Mime-Version: 1.0
  11. Content-Type: text/plain; charset="us-ascii"
  12. Content-Transfer-Encoding: 7bit
  13. X-Nntp-Posting-Host: bajor-le1.trcinc.com
  14. X-Mailer: Mozilla 2.01Gold (WinNT; I)
  15. X-Lines: 16
  16. Content-Length: 703
  17. Originator: clamage@taumet
  18.  
  19. I have noticed, while working on the standard string class, that the 
  20. char_traits functions copy, move, etc, would be much more useful if they 
  21. returned a pointer to the END of the area in which they worked, rather 
  22. than to the beginning.
  23.  
  24. I know c liked to return the pointers you gave it when it was done with 
  25. them, but isn't there something more useful that could be done?
  26.  
  27. Also, when these functions get a string that contains eos(), do they 
  28. stop, or do they carry on to the bitter end?
  29.  
  30. -- 
  31. #include <legalbs/standarddisclaimer>
  32. Rich Paul                |  If you like what I say, tell my
  33. C++, OOD, OOA, OOP,      |  employer, but if you don't,
  34. OOPs, I forgot one ...   |  don't blame them.  ;->
  35.  
  36.  
  37. [ comp.std.c++ is moderated.  To submit articles: try just posting with      ]
  38. [ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu         ]
  39. [ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
  40. [ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
  41. [ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]
  42.